約 6,283,744 件
https://w.atwiki.jp/gamemusicbest100/pages/9920.html
サキュバスアカデミア 機種:PC 作曲者:Cres. 開発元:SQDT 発売年:2021 概要 R18同人ゲームに多大な影響を及ぼしたサークルSQDTが、長きに渡る沈黙を破り公開した作品。 前作『Succubus Quest 短編 -老司書の短い夢-』から実に14年ぶりの新作となった。 コンセプトは「敗北をプレイする、新感覚RPG」。 夢魔の襲来をきっかけに夢の世界と混ざり合ってしまった学園を舞台に、主人公たちは自身の命を犠牲にしながら事態の収拾に奔走することとなる。 ゲーム全編を通じて不条理で幻想的な世界観が保たれており、楽曲もそれに合わせた雰囲気を纏っている。 2022年には『サキュバスアカデミア アペンド ―千変狐と自宅巫女―』が発売。 こちらは東洋をフィーチャーした新シナリオを追加するもので、それに伴い9曲の新規楽曲が追加された。 収録曲(サウンドトラック順) 曲名 作曲・編曲者 補足 順位 Welcome to Academia Cres. タイトル画面 Lightning Cres. オープニング Town 夢度1 ゆがむ世界 Cres. 拠点(1段階目) AttaX Cres. 通常戦闘 Town 夢度2 まざる世界 Cres. 拠点(2段階目) Perilous AttaXXX Cres. 中ボス戦 Open Air Cres. グラウンド渓谷 Mystic River Cres. ボス戦前半パート 第14回410位 Town 夢度3 とける世界 Cres. 拠点(3段階目) Wonderland March Cres. 鏡の国の自習時間 Devourer Cres. ボス戦後半パート Town 夢度4 かわる世界 Cres. 拠点(4段階目) Grave Dance Cres. ホーンテッド理科室 ぬくもり / Kindness Cres. ムネモシュネ戦 Town 夢度5 なじむ世界 Cres. 拠点(5段階目) 沼 / Morass Cres. ヒミツの隠り世 Falcon Cres. ノトーリアス戦 第14回129位第15回560位第16回569位 Town 夢度∞ ゆめの世界 Cres. 拠点(6段階目) Lonely Cres. 幽冥の裂け目 Emptiness Cres. ラスボス戦 第14回293位 End of Academia Cres. エンディング 弦楽四重奏のためのAttaX / AttaX for String Quartet Cres. ボーナストラック(通常戦闘アレンジ) 『サキュバスアカデミア アペンド ―千変狐と自宅巫女―』追加楽曲 Defy me and make my day Cres. アペンド通常戦闘 Egoist Paramount Cres. ダッキ戦 杜の道 Cres. 悠久の通学路 Mara Herself Cres. カヨウ戦 All Leave Me Behind Cres. タマモ戦 蛇使いの街 Cres. 上天の還り路 Mindblower Cres. アペンドボス戦 再見 Cres. アペンドラスボス戦 湧水の地 Cres. 常雨街 サウンドトラック サキュバスアカデミア ORIGINAL SOUNDTRACK サキュバスアカデミア アペンド ―千変狐と自宅巫女― ORIGINAL SOUNDTRACK
https://w.atwiki.jp/marisachan_tairiku/pages/20.html
http //kampa.me/t/bpo
https://w.atwiki.jp/silencekiss/pages/53.html
The Dark Knight ダークナイト [Blu-ray] The night is darkest just before the dawn. And I promise you, the dawn is coming. Why so serious?
https://w.atwiki.jp/android/pages/120.html
2010/3/28 Money Saving Apps For iPhone ( Blackberry/Android) | Money Watch Zenonia now available on the Android Market | AndroidSPIN Google Denies Revenue Sharing For Android Mobile Apps | Ozablog.com Asphault 5 For Android | Android Community Softbank to Sell Its First Android-Based Smartphone in April | BusinessWeek HTC Evo 4G, Nexus One, and Droid – Android Evolution | My Gadget News 『AppBrain』ならウェブ上でAndroidアプリを管理できる | Lifehacker HTC Desire X06HT(SoftBank/HTC):業界最速動画レビュー | YouTube ソフトバンク、Android 2.1搭載端末「HTC Desire X06HT」 - 4月下旬発売 | マイコミジャーナル ソフトバンク、Android 2.1搭載の「HTC Desire」を4月下旬に発売 | ITmedia +D モバイル 高性能なAndroid™ 搭載スマートフォン「HTC Desire™」が登場 | SoftBank 【速報】ソフトバンクモバイル、Androidスマートフォン「HTC Desire(X06HT)」を正式発表 | GIGAZINE Google Denies Revenue Sharing For Android Mobile Apps | eWeek.com CTIA Spring 2010 Super Smartphones and Mighty Messaging Phones | PCWorld Sony Ericsson Xperia X10 to Get Android 2.1 Update | CoolTechZone Android向け「ドコモマーケット」4月1日から 音楽配信やゲームなど提供 | ITmedia story category AT T Locks Down Android Tight | dslreports.com IVR Technologies, Inc. Releases Google™ Android™ Smartphone Application for Mobile International Toll Bypass | PR.com Motorola i1 Push-To-Talk Android Based Smartphone Features Review | SOLID BLOGGER Google Android Still Getting Strong Support | Mobiledia Mystique – Android’s Most Horrifying Puzzle | AndroidGuys Try the ‘Obama for Android’ App for Free | IntoMobile LogMeIn Remote Access App for Android OS in Development | Brighthand.com Get your iTunes music on your phone with MP3tunes | Android Community Famed iPhone RPG Zenonia hits Android, for $5.99 and 1.6 phones and above | EuroDroid Samsung Galaxy S Sports The Fastest GPU In Android Phones | ubergizmo Android This Week Enter the EVO; Samsung Does Android; Nexus One a Success | GigaOM 2010/3/27 Verizon Wireless suggests Android apps for staying organized | IntoMobile CTIA 2010はAndroid一色–各社いよいよ本腰だ | TechCrunch Japan Lenovo Le(楽)Phoneの正式型番は「3GW100」に決定 | Android/OPhone雑記 This is Android domination | AndroidSPIN SlashGear Reviews The X10 | Android Community Google ad revenue sharing isn t Android-specific | Electronista HTC EVO 4G Better Than the Nexus One? | PCWorld Android, Spectrum Talk Dominate CTIA Wireless Conference | All Things Digital No Surprise Google Offers Carriers Rev Sharing | Android Phone Fans HTC Hero update to Android 2.1 on April 26th in home country of Taiwan | Engadget Android boasts 7 of 10 top smartphones in the United States | Android and Me
https://w.atwiki.jp/android/pages/113.html
2010/2/28 New Market Report Android Smartphone Marketplace | PR-inside The Android revolution | AndroidSPIN Video Nexus One vs. Motorola Milestone Google Earth | Phone Reviews Nexus One Mods coming down the pipe in full force | IntoMobile All US Android Phones to Get Android 2.1? | The Unlockr TigerText, an app for keeping messages private | The Money Times Shadow Warrior | Indianexpress.com モトローラOPhone MT710 利用レポート4『MobileMarket編』- 後編 | Android/OPhone雑記 モトローラOPhone MT710 利用レポート4『MobileMarket編』- 前編 | Android/OPhone雑記 Are you kidding me Microsoft? Why confuse with Windows Phone Starter Edition? | ZDNet Android 2.1 Coming to All U.S. Android Phones? (RUMOR) | Mashable 7 Android Devices That Aren t Phones | PCWorld Android phone + audiobook + auto | Booklist Online Verizon Nexus One to get March 23rd debut? | Android Community Slacker Radio 3.0 for BlackBerry Android Brings Faster App and Improved Wireless Station Caching | Gear Diary Android Virtual Doorman Hackery | Android Phone Fans All Android Phones in the U.S. Will Receive an Upgrade to Android 2.1 | Lifehacker Firefox Mobile Browser Fennec Spotted on Android | PCWorld TigerText The App for Spies and Cheaters | PCWorld Rumor Android 2.1 update coming to all U.S. Android phones | Androinica All U.S. Android phones to receive Android 2.1, but some will require a wipe | AndroidSPIN Android This Week Devour Launches, Slacker Caches, Alex Gets Delayed | GigaOM Nexus One for Verizon Wireless Coming in March | infoSync 2010/2/27 All U.S. Android phones to receive Android 2.1, but some will require a wipe | Android and Me TigerText app removes embarrassing text messages | smh.com.au Can Anyone Rescue Palm From Its Death Spiral? | Barrons.com 35 Ultimate Useful Android Applications | Smashing Buzz Work continues on Firefox for Android | Android Central Android is for Boys? 73 Percent of Users Are Male | Tom s Guide Motorola Devour Smartphone | Wired Product Review Android may outsell iPhone in flyover states, thanks to AT T | VentureBeat Flash 10.1 limited to specific hardware standards, excludes early Android smartphones | IntoMobile This Week In Geek Mobile Hacks, Power Concepts, and Hands-On Computing | PCWorld Android pulls ahead of Windows Mobile as hottest trending mobile OS | IntoMobile
https://w.atwiki.jp/yoshiumi41/pages/98.html
?xml version="1.0" encoding="utf-8"? ListView xmlns android="http //schemas.android.com/apk/res/android" android id="@+id/lv_fruit" android layout_width="match_parent" android layout_height="match_parent" android entries="@array/lv_fruit" /ListView
https://w.atwiki.jp/memodroid/pages/18.html
・Android Market非対応 ・ユーザーフォーラム的なもの ・2010/01頃からAmazonで在庫切れ ・液晶は静電式ではなく感圧式(抵抗膜式) ・BIGLOBEでモニター募集をしていた Camangi WebStation – Product specs and features
https://w.atwiki.jp/android/pages/101.html
2010/1/3 モトローラ『XT701』間もなく発売? | Android/OPhone雑記 Google schedules Android announcement | GoErie.com Picture of Motorola Shadow leaked, inverted on Taiwanese forum | Engadget Android で再開する Java プログラミング(13) - Android Market で作品を公開しよう! | 八角研究所 WordPress Android App Coming Soon (RUMOR) | Mashable Android Motorola Droid and HTC Hero Review from an iPhone Perspective — Smartphone Round Robin | The iPhone Blog HTC Android Tablet to debut at CES, HTC Chrome OS Tablet to follow | PMP Today Wordpress App For Google Android Could Be Just Around The Corner | IndyPosted WordPress mobile app for Google Android might be coming soon | Tech Whack Sony Ericsson XPERIA X10 エミュレータを試してみた | adakoda SmartQ V5 HD Android MID Released, Costs US$162 | iTech News Net Android phone with 4.3 inch display for Motorola? | Phone Reviews 2010/1/2 Androidの中国語商標は『安致』 | Android/OPhone雑記 2010年の中国携帯電話市場 | gihyo.jp 2010年に大きく伸びる技術トップテン–タブレットからソーシャルCRMまで | TechCrunch Japan Foxconn denies Orange-branded Android devices | afterdawn.com Google Nexus One Buzz Busted By Harsh Reality Check | Google Watch Android Resources + SQLite. | HatSix Will Android kill the iPhone in 2010? | IPHONETOUCH.BLORGE WordPress Android App Coming Soon (RUMOR) | TechNews.AM RUMOR WordPress Creating An Official Android App For Google | The Blog Hearald 2010年クラウドとスマートフォンがビジネスシーンに普及するためのハードル | ZDNet Japan Android, Chrome outpace iPhone, Safari in web use | Electronista Ten Technologies That Will Rock 2010 | The Washington Post CES 2010 Preview and first look | Examiner.com Droid’s Android 2.1 ROM ‘fully functional’ on G1 | IntoMobile Palm’s webOS App Catalog celebrates the New Year with 1,000th webOS app! | IntoMobile Grooveshark Mobile Music Now Available for Android and BlackBerry | IntoMobile HTC to launch tablets based on Android, Chrome OS? | Unwired View New 7 Android Home Tablet Coming | I4U News Google Nexus Offers Little Competition to Apple iPhone | ABC News Google mounts a big WAC attack on Microsoft in the enterprise | KMWorld 2010/1/1 OPhone 2.0の足音 | Android/OPhone雑記 Rumored Moto Shadow/Mirage sports 4.3-inch touchscreen, 1080p playback | Android Central HTC rumored to have tablet in the works, will show privately at CES | Android Central Android 2.0 vs iPhone How Google could kill the iPhone this year | Electricpig Two Android Powered Motorola Phones to Watch for at CES | CoolTechZone.com HTC Bringing Android Tablet To CES 2010? | I4U News Motorola Shadow Will Have 4.3-inch Display, Android | CoolTechZone.com Google sends invitations for ‘Android press gathering’ to launch Nexus One mobile phone | Caymanmama.com Google’s Android Competes Against iPhone | iPhone-scoop.com General Mobile reveals its Android 2.0 COSMOS smartphone | Mobile Burn Want to see Google s new phone on YouTube? | CNET LG LS680 Android phone | LetsGoMobile Motorola s Rumored Superthin Android Phone Sounds Spectacular | GIZMODO Rumor Motorola to launch two new Android phones with OLED displays | IntoMobile Motorola Android phone leaks with 1080p video, HDMI | Electronista Android 2.1 Gallery App For Motorola DROID | ubergizmo Starcraft2, Real Estate, and Android Apps – Big Opportunities in 2010 | ShoeMoney Samsung i899 does EV-DO, AMOLED, Android for China | Engadget Mobile The Androidification of Everything | BusinessWeek Motorola May Unveil New Android Phones at CES | InternetNews.com Google Android Press Event Next Week | Crispy Gamer Verizon to Reportedly Get Palm Pre Plus, Pixi Plus | eWeek How To Make Your Own Android Doll | Android Guys Motorola Might Be Prepping an Android Smartphone with a 4.3-inch Screen | Brighthand.com First five... Android apps to download | Pocket-lint Ten reasons why an Android phone is not a phone for me. | The Next Web TiPb Presents iPhone Live! #82 — Android and Windows and Tablets… Oh, My! | The iPhone Blog Google Never Mind the Nexus One, How About a Cheaper Cell Plan? | PC World 2010年以降、スマートフォンとケータイは近づいていく──NTTドコモ 辻村氏に聞く(前編) (1/2) | ITmedia +D モバイル
https://w.atwiki.jp/android/pages/146.html
2010/7/12 TwitterライクなAndroid対応組織内情報共有ツール、日本人が設立した中国企業が | ITPro Google launches do-it-yourself apps for Android | VentureBeat Sony Ericsson XPERIA X10 Mini Pro in India for Rs.16000 | fone arena Motorola WX445 Android Phone Leaked | fone arena Google’s Do-It-Yourself App Creation Software | The New York Times Only Android Gains Share | InformationWeek 「AppleとFacebookは脅威ではない」とGoogle CEO | ITmedia Google App Inventor Lets Anyone Make Android Smartphone Apps | PCWorld Fujitsu Gearing Up To Release An Android-powered Phone In Japan | ubergizmo Google、誰でもAndroidアプリを開発できるツール「App Inventor」 | ITmedia 懐かしのGraffitiがAndroidで復活ですよ | ライフハッカー日本版 RIM, Apple Smartphone Leaders, Android Gaining | InformationWeek Verizon Motorola WX445 leaks budget Android phone | AndroidCommunity Using HTC EVO 4G as a Wireless Keyboard and Multitouch Trackpad for Computer | GadgetsDNA Google s master Android plan We re all mobile app developers now | ZDNet Motorola Droid X, The Latest Android, Comes July 15 | LA News Monitor Sprint s EVO 4G Plagued by Component Shortages | DailyTech 米国でAndroidユーザーが大幅増加、携帯でのSNSやWeb利用増える | マイコミジャーナル バージョンアップが待ち切れないあなたへ! Android 1.5&1.6を最新風に変える秀逸アプリ | ギズモード・ジャパン Hey Fring, AT T understands; iPhone owners bring Skype support to its knees | ZDNet Low End Android Phone “Mororola WX445″ Heading to Verizon | My Gadgets News Android Still Gaining Ground | Hard OCP iPhoneからAndroidの乗り換えでカルチャーショックを受けないためのガイド | ライフハッカー日本版 googleとAppleの紳士協定、最初に裏切ったのはどっち?【湯川】 | TechWave コンシューマ戦略が迷走? Microsoftが発売6週間で「Kin」撤退 | クラウドWatch Find Open Parking Spots Via Android’s Open Spot | Hard OCP The Unofficial Android Sonos Controller | Zatz Not Funny! Google Open Spot lets Android users find free parking spaces | SlipperyBrick Add Amazing New Features to Your Phone and Camera | PCWorld iPhone 4 customer parody stings | CNET Low-End Android Phone for Verizon, Leaked | everythingandroid Cyanogen launches Android 2.2 ROM for G1 and MyTouch3G | fone arena HTC Not Looking to Release an Android Tablet Anytime Soon | Android Phone Fans Fujitsu the Latest to Jump On Android Smartphone Bandwagon | GIZMODO やっぱりAndroid 2.2は速かった | ITPro
https://w.atwiki.jp/android/pages/23.html
Eclipseプラグインを使ったAndroidアプリケーションの作成 Eclipseプラグインを使わないAndroidアプリケーションの作成 |######ここまで翻訳######| Implementing Activity Callbacks Opening a New ScreenOpening a Screen Some Intent examples Returning a Result from a Screen Lifetime of the new screen Listening for Button Clicks Configuring General Window Properties Storing and Retrieving StateStoring and Retrieving Larger or More Complex Persistent Data Playing Media Files Listening For and Broadcasting Global Messages, and Setting AlarmsSending the message Receiving the message Other system messages Listening for phone events Setting Alarms Displaying AlertsNormal Alerts AlertDialog Notifications Displaying a Progress Bar Adding Your Application to the Favorites List Adding Items to the Screen MenuAdding Submenus Adding yourself to menus on other applications The offering application Display a Web Page Binding to Data Capture Images from the Phone Camera Handling Expensive Operations in the UI Thread Selecting, Highlighting, or Styling Portions of Text List of Files for an Android Application Eclipseプラグインを使ったAndroidアプリケーションの作成 Android Eclipseプラグインを使用することは、新しいAndroidアプリケーションの作成を始める最も高速で最も簡単な方法です。 プラグインは自動的にあなたのアプリケーションのために正しいプロジェクト構造を生成し、リソースを自動的にコンパイルしてくれます。 Androidアプリケーションの動作原理を理解するために、Androidアプリケーション解体新書を読んでみるのもよいでしょう。 SDKの sample/ フォルダでApiDemosアプリケーションと他のサンプルアプリケーションを見てみることもお勧めします。 最終的にはHello AndroidとNotepadのコードチュートリアルを行うことがEclipseでのAndroid開発を始めるには素敵な方法です。 特にHello Androidチュートリアルを行うことは、Eclipseで新しいAndroidアプリケーションを作成するための優れた導入方法となるでしょう。 Eclipseプラグインを使わないAndroidアプリケーションの作成 |######ここまで翻訳######| This topic describes the manual steps in creating an Android application. Before reading this, you should read Overview of an Android Application to understand the basics of how an Android application works. You might also want to look at the sample applications that ship with Android under the samples/ directory. Here is a list of the basic steps in building an application. 1. Create your required resource files This includes the AndroidManifest.xml global description file, string files that your application needs, and layout files describing your user interface. A full list of optional and required files and syntax details for each is given in File List for an Android Application. 2. Design your user interface See Implementing a UI for details on elements of the Android screen. 3. Implement your Activity (this page) You will create one class/file for each screen in your application. Screens will inherit from an android.app class, typically android.app.Activity for basic screens, android.app.ListActivity for list screens, or android.app.Dialog for dialog boxes. You will implement the required callbacks that let you draw your screen, query data, and commit changes, and also perform any required tasks such as opening additional screens or reading data from the device. Common tasks, such as opening a new screen or reading data from the device, are described below. The list of files you ll need for your application are described in List of Files for an Android Application. 4. Build and install your package. The Android SDK has some nice tools for generating projects and debugging code. Implementing Activity Callbacks Android calls a number of callbacks to let you draw your screen, store data before pausing, and refresh data after closing. You must implement at least some of these methods. See Lifetime of a Screen to learn when and in what order these methods are called. Here are some of the standard types of screen classes that Android provides android.app.Activity - This is a standard screen, with no specialization. android.app.ListActivity - This is a screen that is used to display a list of something. It hosts a ListView object, and exposes methods to let you identify the selected item, receive callbacks when the selected item changes, and perform other list-related actions. android.app.Dialog - This is a small, popup dialog-style window that isn t intended to remain in the history stack. (It is not resizeable or moveable by the user.) Opening a New Screen Your Activity will often need to open another Activity screen as it progresses. This new screen can be part of the same application or part of another application, the new screen can be floating or full screen, it can return a result, and you can decide whether to close this screen and remove it from the history stack when you are done with it, or to keep the screen open in history. These next sections describe all these options. Floating or full? When you open a new screen you can decide whether to make it transparent or floating, or full-screen. The choice of new screen affects the event sequence of events in the old screen (if the new screen obscures the old screen, a different series of events is called in the old screen). See Lifetime of an Activity for details. Transparent or floating windows are implemented in three standard ways Create an app.Dialog class Create an app.AlertDialog class Set the Theme_Dialog theme attribute to @android style/Theme.Dialog in your AndroidManifest.xml file. For example activity class="AddRssItem" android label="Add an item" android theme="@android style/Theme.Dialog"/ Calling startActivity() or startSubActivity() will open a new screen in whatever way it defines itself (if it uses a floating theme it will be floating, otherwise it will be full screen). Opening a Screen When you want to open a new screen, you can either explicitly specify the activity class to open, or you can let the operating system decide which screen to open, based upon the data and various parameters you pass in. A screen is opened by calling startActivity and passing in an Intent object, which specifies the criteria for the handling screen. To specify a specific screen, call Intent.setClass or setClassName with the exact activity class to open. Otherwise, set a variety of values and data, and let Android decide which screen is appropriate to open. Android will find one or zero Activities that match the specified requirements; it will never open multiple activities for a single request. More information on Intents and how Android resolves them to a specific class is given in the Intent topic. Some Intent examples The following snippet loads the com.google.android.samples.Animation1 class, and passes it some arbitrary data. Intent myIntent = new Intent(); myIntent.component = "com.google.android.samples.Animation1"; myIntent.putExtra("com.google.android.samples.SpecialValue", "Hello, Joe!"); // key/value pair, where key needs current package prefix. startActivity(myIntent); The next snippet requests that a Web page be opened by specifying the VIEW action, and a URI data string starting with "http //" schema Intent myIntent = new Intent("android.intent.action.VIEW", "http //www.google.com"); myIntent.putExtra("com.google.android.samples.SpecialValue", "Hello, Joe!"); // key/value pair, where key needs current package prefix. Here is the intent filter from the AndroidManifest.xml file for com.google.android.browser intent-filter action value="android.intent.action.VIEW" / category value="android.intent.category.DEFAULT" / scheme value="http" / scheme value="https" / scheme value="file" / /intent-filter Android defines a number of standard values, for instance the action constants defined by Intent. You can define custom values, but both the caller and handler must use them. See the intent-filter tag description in AndroidManifest.xml File Details for more information on the manifest syntax for the handling application. Returning a Result from a Screen A window can return a result after it closes. This result will be passed back into the calling Activity s onActivityResult() method, which can supply an integer result code, a string of data, and a Bundle of arbitrary data, along with the request code passed to startSubActivity(). Note that you must call the startSubActivity() method that accepts a request code parameter to get this callback. The following code demonstrates opening a new screen and retrieving a result. // Open the new screen. public void onClick(View v){ // Start the activity whose result we want to retrieve. The // result will come back with request code GET_CODE. Intent intent = new Intent(this, com.example.app.ChooseYourBoxer.class); startSubActivity(intent, CHOOSE_FIGHTER); } // Listen for results. protected void onActivityResult(int requestCode, int resultCode, String data, Bundle extras){ // See which child activity is calling us back. switch (resultCode) { case CHOOSE_FIGHTER // This is the standard resultCode that is sent back if the // activity crashed or didn t doesn t supply an explicit result. if (resultCode == RESULT_CANCELED){ myMessageboxFunction("Fight cancelled"); } else { myFightFunction(data, extras); } default break; } } // Class SentResult // Temporary screen to let the user choose something. private OnClickListener mLincolnListener = new OnClickListener(){ public void onClick(View v) { Bundle stats = new Bundle(); stats.putString("height","6\ 4\""); stats.putString("weight", "190 lbs"); stats.putString("reach", "74\""); setResult(RESULT_OK, "Lincoln", stats); finish(); } }; private OnClickListener mWashingtonListener = new OnClickListener() { public void onClick(View v){ Bundle stats = new Bundle(); stats.putString("height","6\ 2\""); stats.putString("weight", "190 lbs"); stats.putString("reach", "73\""); setResult(RESULT_OK, "Washington", Bundle); finish(); } }; Lifetime of the new screen An activity can remove itself from the history stack by calling Activity.finish() on itself, or the activity that opened the screen can call Activity.finishSubActivity() on any screens that it opens to close them. Listening for Button Clicks Button click and other UI event capturing are covered in Listening for UI Notifications on the UI Design page. Configuring General Window Properties You can set a number of general window properties, such as whether to display a title, whether the window is floating, and whether it displays an icon, by calling methods on the Window member of the underlying View object for the window. Examples include calling getWindow().requestFeature() (or the convenience method requestWindowFeature(some_feature)) to hide the title. Here is an example of hiding the title bar //Hide the title bar requestWindowFeature(Window.FEATURE_NO_TITLE); Storing and Retrieving State If your application is dumped from memory because of space concerns, it will lose all user interface state information such as checkbox state and text box values as well as class member values. Android calls Activity.onFreeze before it pauses the application. This method hands in a Bundle that can be used to store name/value pairs that will persist and be handed back to the application even if it is dropped from memory. Android will pass this Bundle back to you when it calls onCreate(). This Bundle only exists while the application is still in the history stack (whether or not it has been removed from memory) and will be lost when the application is finalized. See the topics for onFreeze(Bundle) and onCreate(Bundle) for examples of storing and retrieving state. Read more about the life cycle of an application in Lifetime of an Activity. Storing and Retrieving Larger or More Complex Persistent Data Your application can store files or complex collection objects, and reserve them for private use by itself or other activities in the application, or it can expose its data to all other applications on the device. See Storing, Retrieving, and Exposing Data to learn how to store and retrieve private data, how to store and retrieve common data from the device, and how to expose your private data to other applications. Playing Media Files Please see the document Android Media APIs for more details. Listening For and Broadcasting Global Messages, and Setting Alarms You can create a listening class that can be notified or even instantiated whenever a specific type of system message is sent. The listening classes, called intent receivers, extend IntentReceiver. If you want Android to instantiate the object whenever an appropriate intent notification is sent, define the receiver with a receiver element in the AndroidManifext.xml file. If the caller is expected to instantiate the object in preparation to receive a message, this is not required. The receiver will get a call to their IntentReceiver.onReceiveIntent() method. A receiver can define an intent-filter tag that describes the types of messages it will receive. Just as Android s IntentResolver will look for appropriate Activity matches for a startActivity() call, it will look for any matching Receivers (but it will send the message to all matching receiver, not the "best" match). To send a notification, the caller creates an Intent object and calls Activity.broadcastIntent() with that Intent. Multiple recipients can receive the same message. You can broadcast an Intent message to an intent receiver in any application, not only your own. If the receiving class is not registered using receiver in its manifest, you can dynamically instantiate and register a receiver by calling Context.registerReceiver(). Receivers can include intent filters to specify what kinds of intents they are listening for. Alternatively, if you expect a single known caller to contact a single known receiver, the receiver does not specify an intent filter, and the caller specifies the receiver s class name in the Intent by calling Intent.setClassName() with the recipient s class name. The recipient receives a Context object that refers to its own package, not to the package of the sender. Note If a receiver or broadcaster enforces permissions, your application might need to request permission to send or receive messages from that object. You can request permission by using the uses-permission tag in the manifest. Here is a code snippet of a sender and receiver. This example does not demonstrate registering receivers dynamically. For a full code example, see the AlarmService class in the ApiDemos project. Sending the message // We are sending this to a specific recipient, so we will // only specify the recipient class name. Intent intent = new Intent(this, AlarmReceiver.class); intent.putExtra("message","Wake up."); broadcastIntent(intent); Receiving the message Receiver AndroidManifest.xml (because there is no intent filter child, this class will only receive a broadcast when the receiver class is specified by name, as is done in this example) receiver class=".AlarmReceiver" / Receiver Java code public class AlarmReceiver extends IntentReceiver{ // Display an alert that we ve received a message. @Override public void onReceiveIntent(Context context, Intent intent){ // Send a text notification to the screen. NotificationManager nm = (NotificationManager) context.getSystemService(Context.NOTIFICATION_SERVICE); nm.notifyWithText(R.id.alarm, "Alarm!!!", NotificationManager.LENGTH_SHORT, null); } } Other system messages You can listen for other system messages sent by Android as well, such as USB connection/removal messages, SMS arrival messages, and timezone changes. See Intent for a list of broadcast messages to listen for. Messages are marked "Broadcast Action" in the documentation. Listening for phone events The telephony package overview page describes how to register to listen for phone events. Setting Alarms Android provides an AlarmManager service that will let you specify an Intent to send at a designated time. This intent is typically used to start an application at a preset time. (Note If you want to send a notification to a sleeping or running application, use Handler instead.) Displaying Alerts There are two major kinds of alerts that you may display to the user (1) Normal alerts are displayed in response to a user action, such as trying to perform an action that is not allowed. (2) Out-of-band alerts, called notifications, are displayed as a result of something happening in the background, such as the user receiving new e-mail. Normal Alerts Android provides a number of ways for you to show popup notifications to your user as they interact with your application. Class Description app.AlertDialogorContext.showAlert() A popup alert dialog with two buttons (typically OK and Cancel) that take callback handlers. It can be created separately, or launched using the Application helper method Context.showAlert(). See the section after this table for more details. ProgressDialog A dialog box used to indicate progress of an operation with a known progress value or an indeterminate length (setProgress(bool)). See Views Progress Bar in ApiDemos for examples. Activity By setting the theme of an activity to android theme="android style/Theme.Dialog", your activity will take on the appearance of a normal dialog, floating on top of whatever was underneath it. You usually set the theme through the android theme attribute in your AndroidManifest.xml. The advantage of this over Dialog and AlertDialog is that Application has a much better managed lifecycle than dialogs if a dialog goes to the background and is killed, you cannot recapture state, whereas Application exposes a Bundle of saved values in onCreate() to help you maintain state. AlertDialog This is a basic warning dialog box that lets you configure a message, button text, and callback. You can create one by calling the Application helper method Context.showAlert(), as shown here. private Handler mHandler = new Handler() { public void handleMessage(Message msg) { switch (msg.what) { case ACCEPT_CALL answer(msg.obj); break; case BOUNCE_TO_VOICEMAIL voicemail(msg.obj); break; } } }; private void IncomingMotherInlawCall(Connection c) { String Text; // "Answer" callback. Message acceptMsg = Message.obtain(); acceptMsg.target = mHandler; acceptMsg.what = ACCEPT_CALL; acceptMsg.obj = c.getCall(); // "Cancel" callback. Message rejectMsg = Message.obtain(); rejectMsg.target = mHandler; rejectMsg.what = BOUNCE_TO_VOICEMAIL; rejectMsg.obj = c.getCall(); showAlert(null, "Phyllis is calling", "Answer", acceptMsg, true, rejectMsg); } Notifications Out-of-band alerts should always be displayed using the NotificationManager, which allows you to tell the user about something they may be interested in without disrupting what they are currently doing. A notification can be anything from a brief pop-up box informing the user of the new information, through displaying a persistent icon in the status bar, to vibrating, playing sounds, or flashing lights to get the user s attention. In all cases, the user must explicitly shift their focus to the notification before they can interact with it. The following code demonstrates using NotificationManager to display a basic text popup when a new SMS message arrives in a listening service, and provides the current message count. You can see several more examples in the ApiDemos application, under app/ (named notification*.java). static void setNewMessageIndicator(Context context, int messageCount){ // Get the static global NotificationManager object. NotificationManager nm = NotificationManager.getDefault(); // If we re being called because a new message has been received, // then display an icon and a count. Otherwise, delete the persistent // message. if (messageCount 0) { nm.notifyWithText(myApp.NOTIFICATION_GUID, // ID for this notification. messageCount + " new message" + messageCount 1 ? "s" "", // Text to display. NotificationManager.LENGTH_SHORT); // Show it for a short time only. } } To display a notification in the status bar and have it launch an intent when the user selects it (such as the new text message notification does), call NotificationManager.notify(), and pass in vibration patterns, status bar icons, or Intents to associate with the notification. Displaying a Progress Bar An activity can display a progress bar to notify the user that something is happening. To display a progress bar in a screen, call Activity.requestWindowFeature(Window.FEATURE_PROGRESS). To set the value of the progress bar, call Activity.getWindow().setFeatureInt(Window.FEATURE_PROGRESS, level). Progress bar values are from 0 to 9,999, or set the value to 10,000 to make the progress bar invisible. You can also use the ProgressDialog class, which enables a dialog box with an embedded progress bar to send a "I m working on it" notification to the user. Adding Your Application to the Favorites List You can t. Only a user can add an application to the Favorites list. Adding Items to the Screen Menu Every Android screen has a default menu with default options, such as adding the activity to the favorites menu. You can add your own menu entries to the default menu options by implementing Activity.onCreateOptionsMenu or Activity.onPrepareOptionsMenu(), and adding Item objects to the Menu passed in. To handle clicks implement Activity.onOptionsItemSelected() to handle the click in your Activity class. You may also pass the Item object a handler class that implements the Runnable class (a handler) but this is less efficient and discouraged. An application receives a callback at startup time to enable it to populate its menu. Additionally, it receives callbacks each time the user displays the options menu to let you perform some contextual modifications on the menu. To populate the menu on startup, override Activity.onCreateOptionsMenu; to populate it when the menu is called (somewhat less efficient), you can override Activity.onPrepareOptionsMenu(). Each Activity has its own menu list. Menu items are displayed in the order added, though you can group them as described in the Menu.add documentation. The following code snippet adds three items to the default menu options and handles them through the overridden Activity.onOptionsItemSelected() method. You can show or hide menu items by calling setItemShown() or setGroupShown(). // Called only the first time the options menu is displayed. // Create the menu entries. // Menu adds items in the order shown. @Override public boolean onCreateOptionsMenu(Menu menu) { super.onCreateOptionsMenu(menu); // Parameters for menu.add are // group -- Not used here. // id -- Used only when you want to handle and identify the click yourself. // title menu.add(0, 0, "Zoom"); menu.add(0, 1, "Settings"); menu.add(0, 2, "Other"); return true; } // Activity callback that lets your handle the selection in the class. // Return true to indicate that you ve got it, false to indicate // that it should be handled by a declared handler object for that // item (handler objects are discouraged for reasons of efficiency). @Override public boolean onOptionsItemSelected(Menu.Item item){ switch (item.getId()) { case 0 showAlert("Menu Item Clicked", "Zoom", "ok", null, false, null); return true; case 1 showAlert("Menu Item Clicked", "Settings", "ok", null, false, null); return true; case 2 showAlert("Menu Item Clicked", "Other", "ok", null, false, null); return true; } return false; } You can add key shortcuts by calling the Item.setAlphabeticShortcut() or Item.setNumericShortcut() methods, as demonstrated here to add a "C" shortcut to a menu item thisItem.setAlphabeticShortcut(0, c ); Adding Submenus Add a submenu by calling Menu.addSubMenu(), which returns a SubMenu object. You can then add additional items to this menu. Menus can only be one level deep, and you can customize the appearance of the submenu menu item. @Override public boolean onCreateOptionsMenu(Menu menu) { super.onCreateOptionsMenu(menu); // Parameters for menu.add are // group -- Not used here. // id -- Used only when you want to handle and identify the click yourself. // title menu.add(0, 0, "Send message"); menu.add(0, 1, "Settings"); menu.add(0, 2, "Local handler"); menu.add(0, 3, "Launch contact picker"); // Add our submenu. SubMenu sub = menu.addSubMenu(1, 4, "Days of the week"); sub.add(0, 5, "Monday"); sub.add(0, 6, "Tuesday"); sub.add(0, 7, "Wednesday"); sub.add(0, 8, "Thursday"); sub.add(0, 9, "Friday"); sub.add(0, 10, "Saturday"); sub.add(0, 11, "Sunday"); return true; } Adding yourself to menus on other applications You can also advertise your Activity s services so that other Activities can add your activity to their own option menu. For example, suppose you implement a new image handling tool that shrinks an image to a smaller size and you would like to offer this as a menu option to any other Activity that handles pictures. To do this, you would exposes your capabilities inside an intent filter in your manifest. If another application that handles photos asks Android for any Activities that can perform actions on pictures, Android will perform intent resolution, find your Activity, and add it to the other Activity s options menu. The offering application The application offering the service must include an intent-filter element in the manifest, inside the activity tag of the offering Activity. The intent filter includes all the details describing what it can do, such as a type element that describes the MIME type of data that it can handle, a custom action value that describes what your handling application can do (this is so that when it receives the Intent on opening it knows what it is expected to do), and most important, include a category filter with the value android.intent.category.ALTERNATIVE and/or android.intent.category.SELECTED_ALTERNATIVE (SELECTED_ALTERNATIVE is used to handle only the currently selected element on the screen, rather than the whole Activity intent. Here s an example of a snip of a manifest that advertises picture shrinking technology for both selected items and the whole screen. activity class="PictureShrink" !-- Handling class -- intent-filter label="Shrink picture" !-- Menu label to display -- action value="com.example.sampleapp.SHRINK_IT" / type value="image/*" / !-- MIME type for generic images -- category value="android.intent.category.ALTERNATIVE " / category value="android.intent.category.SELECTED_ALTERNATIVE" / /intent-filter /activity The menu-displaying application An application that wants to display a menu that includes any additional external services must, first of all, handle its menu creation callback. As part of that callback it creates an intent with the category Intent.ALTERNATIVE_CATEGORY and/or Intent.SELECTED_ALTERNATIVE, the MIME type currently selected, and any other requirements, the same way as it would satisfy an intent filter to open a new Activity. It then calls menu.addIntentOptions() to have Android search for and add any services meeting those requirements. It can optionally add additional custom menu items of its own. You should implement SELECTED_ALTERNATIVE in onPrepareOptionsMenu() rather than onCreateOptionsMenu(), because the user s selection can change after the application is launched. Here s a code snippet demonstrating how a picture application would search for additional services to display on its menu. @Override public boolean onCreateOptionsMenu(Menu menu){ super.onCreateOptionsMenu(menu); // Create an Intent that describes the requirements to fulfill to be included // in our menu. The offering app must include a category value of Intent.ALTERNATIVE_CATEGORY. Intent intent = new Intent(null, getIntent().getData()); intent.addCategory(Intent.ALTERNATIVE_CATEGORY); // Search for, and populate the menu with, acceptable offering applications. menu.addIntentOptions( 0, // Group 0, // Any unique IDs we might care to add. MySampleClass.class.getName(), // Name of the class displaying the menu--here, its this class. null, // No specifics. intent, // Previously created intent that describes our requirements. 0, // No flags. null); // No specifics. return true; } Display a Web Page Use the webkit.WebView object. Binding to Data You can bind a ListView to a set of underlying data by using a shim class called ListAdapter (or a subclass). ListAdapter subclasses bind to a variety of data sources, and expose a common set of methods such as getItem() and getView(), and uses them to pick View items to display in its list. You can extend ListAdapter and override getView() to create your own custom list items. There are essentially only two steps you need to perform to bind to data 1. Create a ListAdapter object and specify its data source 2. Give the ListAdapter to your ListView object. That s it! Here s an example of binding a ListActivity screen to the results from a cursor query. (Note that the setListAdapter() method shown is a convenience method that gets the page s ListView object and calls setAdapter() on it.) // Run a query and get a Cursor pointing to the results. Cursor c = People.query(this.getContentResolver(), null); startManagingCursor(c); // Create the ListAdapter. A SimpleCursorAdapter lets you specify two interesting things // an XML template for your list item, and // The column to map to a specific item, by ID, in your template. ListAdapter adapter = new SimpleCursorAdapter(this, android.R.layout.simple_list_item_1, // Use a template that displays a text view c, // Give the cursor to the list adapter new String[] {People.NAME} , // Map the NAME column in the people database to... new String[] {"text1"}); // The "text1" view defined in the XML template setListAdapter(adapter); See view/List4 in the ApiDemos project for an example of extending ListAdapter for a new data type. Capture Images from the Phone Camera You can hook into the device s camera onto your own Canvas object by using the CameraDevice class. See that class s documentation, and the ApiDemos project s Camera Preview application (Graphics/Camera Preview) for example code. Handling Expensive Operations in the UI Thread Avoid performing long-running operations (such as network I/O) directly in the UI thread — the main thread of an application where the UI is run — or your application may be blocked and become unresponsive. Here is a brief summary of the recommended approach for handling expensive operations 1. Create a Handler object in your UI thread 2. Spawn off worker threads to perform any required expensive operations 3. Post results from a worker thread back to the UI thread s handler either through a Runnable or a Message 4. Update the views on the UI thread as needed The following outline illustrates a typical implementation public class MyActivity extends Activity { [ . . . ] // Need handler for callbacks to the UI thread final Handler mHandler = new Handler(); // Create runnable for posting final Runnable mUpdateResults = new Runnable() { @Override public void run() { updateResultsInUi(); } }; @Override protected void onCreate(Bundle icicle) { super.onCreate(icicle); [ . . . ] } protected void startLongRunningOperation() { // Fire off a thread to do some work that we shouldn t do directly in the UI thread Thread t = new Thread() { public void run() { mResults = doSomethingExpensive(); mHandler.post(mUpdateResults); } }; t.start(); } private void updateResultsInUi() { // Back in the UI thread -- update our UI elements based on the data in mResults [ . . . ] } } For further discussions on this topic, see Developing Responsive Applications and the Handler documentation. Selecting, Highlighting, or Styling Portions of Text You can highlight or style the formatting of strings or substrings of text in a TextView object. There are two ways to do this If you use a string resource, you can add some simple styling, such as bold or italic using HTML notation. So, for example, in res/values/strings.xml you could declare this resource string id="@+id/styled_welcome_message" We are b i so /i /b glad to see you. /string /resources To style text on the fly, or to add highlighting or more complex styling, you must use the Spannable object as described next. To style text on the fly, you must make sure the TextView is using Spannable storage for the text (this will always be true if the TextView is an EditText), retrieve its text with getText(), and call setSpan(Object, int, int, int), passing in a new style class from the android.text.style package and the selection range. The following code snippet demonstrates creating a string with a highlighted section, italic section, and bold section, and adding it to an EditText object. // Get our EditText object. EditText vw = (EditText)findViewById(R.id.text); // Set the EditText s text. vw.setText("Italic, highlighted, bold."); // If this were just a TextView, we could do // vw.setText("Italic, highlighted, bold.", TextView.BufferType.SPANNABLE); // to force it to use Spannable storage so styles can be attached. // Or we could specify that in the XML. // Get the EditText s internal text storage Spannable str = vw.getText(); // Create our span sections, and assign a format to each. str.setSpan(new StyleSpan(android.graphics.Typeface.ITALIC), 0, 7, Spannable.SPAN_EXCLUSIVE_EXCLUSIVE); str.setSpan(new BackgroundColorSpan(0xFFFFFF00), 8, 19, Spannable.SPAN_EXCLUSIVE_EXCLUSIVE); str.setSpan(new StyleSpan(android.graphics.Typeface.BOLD), 21, str.length() - 1, Spannable.SPAN_EXCLUSIVE_EXCLUSIVE); List of Files for an Android Application The following list describes the structure and files of an Android application. Many of these files can be built for you (or stubbed out) by the activityCreator.py application shipped in the tools/ menu of the SDK. See Building an Android Sample Application for more information on using activityCreator.py. MyApp/ AndroidManifest.xml (required) Advertises the screens that this application provides, where they can be launched (from the main program menu or elsewhere), any content providers it implements and what kind of data they handle, where the implementation classes are, and other application-wide information. Syntax details for this file are described in AndroidManifest.xml. src//myPackagePath/.../MyClass.java (required) This folder holds all the source code files for your application, inside the appropriate package subfolders. res/ (required) This folder holds all the resources for your application. Resources are external data files or description files that are compiled into your code at build time. Files in different folders are compiled differently, so you must put the proper resource into the proper folder. (See Resources for details.) anim/animation1.xml... (optional) Holds any animation XML description files that the application uses. The format of these files is described in Resources. drawable/some_picture.pngsome_stretchable.9.pngsome_background.xml... (optional) Zero or more files that will be compiled to android.graphics.drawable resources. Files can be image files (png, gif, or other) or XML files describing other graphics such as bitmaps, stretchable bitmaps, or gradients. Supported bitmap file formats are PNG (preferred), JPG, and GIF (discouraged), as well as the custom 9-patch stretchable bitmap format. These formats are described in Resources. layout/screen_1_layout.xml... (optional) Holds all the XML files describing screens or parts of screens. Although you could create a screen in Java, defining them in XML files is typically easier. A layout file is similar in concept to an HTML file that describes the screen layout and components. See Implementing a UI for more information about designing screens, and Layout Resources for the syntax of these files. values/arraysclasses.xmlcolors.xmldimens.xmlstrings.xmlstyles.xmlvalues.xml (optional) XML files describing additional resources such as strings, colors, and styles. The naming, quantity, and number of these files are not enforced--any XML file is compiled, but these are the standard names given to these files. However, the syntax of these files is prescribed by Android, and described in Resources. xml/ (optional) XML files that can be read at run time on the device. raw/ (optional) Any files to be copied directly to the device.